1001 Secrets for Windows NT Registry
(Publisher: 29th Street Press)
Author(s): Tim Daniels
ISBN: 1882419685
Publication Date: 12/01/97

Previous Table of Contents Next


I-347 If you need to see what a client’s DHCP parameters were before the most recent changes, you can find them in the following registry entries. Note that you find this out by looking at the ControlSet001 value, which is different from the CurrentControlSet value. To go back one more revision, you can look at ControlSet002 value.

Hive: HKEY_LOCAL_MACHINE
Key: System\ControlSet001\Services\<adapter name>\ Parameters\Tcpip

The following list of DHCP values is available under the Tcpip key:

Value Name: DefaultGateway
Data Type: REG_MULTI_SZ
Value: 0.0.0.0

I-348 Value Name: EnableDHCP
Data Type: REG_DWORD
Value: 0x1

I-349 Value Name: IPAddress
Data Type: REG_MULTI_SZ
Value: 0.0.0.0

I-350 Value Name: PPTPFiltering
Data Type: REG_DWORD
Value: 0

I-351 Value Name: SubnetMask
Data Type: REG_MULTI_SZ
Value: 0.0.0.0

I-352 Value Name: UseZeroBroadcast
Data Type: REG_DWORD
Value: 0

You can edit any of these values. Reboot the machine for changes to take effect.

NETBIOS over TCP (NetBT)

I-353 If a client is having trouble with its NetBT configuration on Windows NT (see the Appendix for instructions for Windows 95) and you want to change or verify some of the settings, you can use the remote capability of Regedt32.exe. Using the Select Computer option, choose the computer you need to access and use these registry keys to view NetBT-related information. Generally, you set these with the Network Control Panel Application; however, it is very useful to be able to view these values remotely.

Hive: HKEY_LOCAL_MACHINE
Key: System\CurrentControlSet\Services\NetBt\Parameters
Value Name: EnableLmhosts
Data Type: REG_DWORD
Value: 1

When this registry entry is set to 1, NetBT uses the LMHOSTS file to resolve any outstanding queries that couldn’t be resolved using WINS or broadcasts.

I-354 Hive: HKEY_LOCAL_MACHINE
Key: System\CurrentControlSet\Services\LanmanServer\ Parameters

Add the following value under the Parameters key:

Value Name: OptionalNames
Data Type: REG_SZ
Value: < any name you want as an alias>

You can then use this alias for any command that requires a server, such as Net Use.

I-355 Hive: HKEY_LOCAL_MACHINE
Key: System\CurrentControlSet\Services\NetBt\Parameters
Value Name: EnableDns
Data Type: REG_DWORD
Value: 0

When this registry entry is set to 1, NetBT uses DNS to resolve queries that it could not resolve with WINS, broadcast, or the LMHOSTS file.

I-356 Hive: HKEY_LOCAL_MACHINE
Key: System\CurrentControlSet\Services\NetBt\Parameters
Value Name: EnableProxy
Data Type: REG_DWORD
Value: 0

When this registry entry is set to 1, the machine acts as a proxy name server for networks that are bound to NetBT. A proxy name server answers other clients’ name queries for system names it has resolved via WINS.

I-357 Hive: HKEY_LOCAL_MACHINE
Key: System\CurrentControlSet\Services\NetBt\Parameters
Value Name: NameServer
Data Type: REG_DWORD
Value: <any valid IP address>

This value is the address of the machine that the client machine uses for WINS queries. The default value is blank.

I-358 Hive: HKEY_LOCAL_MACHINE
Key: System\CurrentControlSet\Services\NetBt\Parameters
Value Name: NameServerBackup
Data Type: REG_DWORD
Value: <any valid IP address>

This is the address of the secondary WINS server. If the machine whose value is stored in NameServer cannot be reached, the machine at this address is queried.

I-359 Hive: HKEY_LOCAL_MACHINE
Key: System\CurrentControlSet\Services\NetBt\Parameters
Value Name: ScopeID
Data Type: REG_DWORD
Value: <any valid DNS domain name> Example: Winntmag.com

This value governs the NetBios name scope. Any valid DNS domain name automatically overrides the DHCP-assigned equivalent.


Previous Table of Contents Next